Record the RFQ backend as a TypeScript SDK and local-reference path before MVP demo backend work begins, while preserving pending PR context for RFQ hardening, E2E, CLI, and BUIDL fixtures.

Constraint: Open PRs #24, #28, #29, #30, and #35 already cover parts of RFQ hardening, protected-router scenarios, live demo, CLI, and BUIDL-like fixtures.
Rejected: Treating an RFQ backend as a Corner Store-operated production server | would blur operator responsibilities for pricing, signer custody, inventory, hosting, and compliance prechecks.
Confidence: high
Scope-risk: narrow
Directive: Implement RFQ SDK interfaces first; any MVP backend must reuse merged E2E/CLI/BUIDL paths instead of creating parallel demo infrastructure.
Tested: git diff --check
Not-tested: services/rfq implementation or runtime tests; documentation-only change

Resolve the stacked PR branch after main advanced with the router venue binding fix, Phase 1 architecture baseline, and RFQ backend SDK documentation/code.

Constraint: PR #24 must merge after #23 and before the higher stacked PRs.

Rejected: Dropping either RFQ-002 or RFQ-SDK documentation state | both are accepted completed work on main/stack.

Confidence: high

Scope-risk: moderate

Directive: Continue stacked PR merges in order after #24 lands: #25, #26, #27, #28, #29, #30.

Tested: git diff --cached --check; scripts/check.sh

Not-tested: GitHub CI after push

Resolve the stacked PR branch after main advanced with RFQ hardening, Phase 1 architecture baseline, and RFQ SDK work.

Constraint: PR #25 must land after #24 and before the higher stacked manifest/E2E/CLI PRs.

Rejected: Keeping duplicate D008 decision numbering | would make the decision log ambiguous after merging RFQ-002 and CMP-001.

Confidence: high

Scope-risk: moderate

Directive: Continue stacked PR merges in order after #25 lands: #26, #27, #28, #29, #30.

Tested: git diff --cached --check

Not-tested: full local scripts/check.sh for this conflict-only reconciliation; rely on GitHub CI after push

Resolve the stacked PR branch after main advanced with RFQ hardening, Reg D compliance elements, Phase 1 architecture baseline, and RFQ SDK work.

Constraint: PR #26 must land after #25 and before the higher stacked RFQ integration/E2E/CLI PRs.

Rejected: Keeping duplicate D009 decision numbering | would make CMP-001 and CMP-002 ambiguous in the decision log.

Confidence: high

Scope-risk: moderate

Directive: Continue stacked PR merges in order after #26 lands: #27, #28, #29, #30.

Tested: git diff --cached --check

Not-tested: full local scripts/check.sh for this conflict-only reconciliation; rely on GitHub CI after push

Resolve the stacked PR branch after main advanced with the manifest lifecycle, Reg D compliance, RFQ hardening, and RFQ SDK work.

Constraint: PR #27 must land after #26 and before RFQ integration/E2E/CLI PRs.

Confidence: high

Scope-risk: narrow

Directive: Continue stacked PR merges in order after #27 lands: #28, #29, #30.

Tested: git diff --check; git diff --cached --check

Not-tested: full local scripts/check.sh for this progress-only reconciliation; rely on GitHub CI after push

Resolve the stacked PR branch after main advanced with RFQ integration and earlier RFQ/compliance work.

Constraint: PR #29 must land after #28 and before the CLI PR.

Confidence: high

Scope-risk: moderate

Directive: Continue stacked PR merges in order after #29 lands: #30.

Tested: git diff --check; git diff --cached --check

Not-tested: full local scripts/check.sh for this progress-only reconciliation; rely on GitHub CI after push